Actually, I believe that this is not quite correct for consuming in an application without that app having to manually build via ember-cli-build.js (which isn't included in in files either).

There is a bit of work going on in the build to make a handlebars package (see here and here), and the rest of the project assumes it can import these from 'handlebars/*' paths (i.e. here). We also assume that you can import directly from simple-html-tokenizer in a few places...

@rwjblue I see your point. For my particular use case, I'm actually requiring Glimmer's ember-cli-build.js file for the build (that's another file that should probably be in the files array), and only using the TypeScript files directly for the type annotations. This is actually modeled on how TypeScript itself is set up.

Still, it seems kind of silly to "build" the TypeScript stuff into dist/. Ideally the weirdness with handlebars/* and simple-html-tokenizer can be addressed more cleanly than by patching it in in a few different, non-standard ways. I think the best bet, ideally, is to consume everything as ES6 modules and use TypeScript's paths feature (only on TS nightly at the moment) to tell the compiler where to find all the dependencies.

@rwjblue Given emberjs/ember.js#13615 and the fact that Ember relies on including the built-in Glimmer ember-cli-build.js, I think we should probably remove the files entry from package.json entirely. At the moment, Ember relies on being able to consume the entire package, and do its own build, from npm.

Now this will make it exclude dist/, which makes CJS not work. Can you add an .npmignore that is roughly a copy of .gitignore but not excluding dist/?

LGTM

@tomdale I think you'll need to rebase

Looks like the build is failing, not sure why yet.

@tomdale - @asakusuma fixed (by pinning typescript version) last night, I restarted the second travis job (one passed and one failed)

YOLO